SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 35112: Invalid binary data when transferring SAS data sets with PROC COPY or CPORT/CIMPORT

DetailsCodeResultsHotfixAboutRate It

MXG makes extensive use of DATA step views and binary data in character fields with $HEXw. and user-written MXG hex formats. The format indicates that the information in the character variable is not character, but binary or hex data.

This data should not be modifed by the transport process when moving from one platform to another. TRANSCODE=NO is required to move character variables containing HEX values that are not to be translated during the transport process. Previously, SAS Views did not honor the TRANSCODE=NO parameter

To make this happen, permanently specify the variable attribute on the SAS data set of TRANSCODE=NO with an ATTRIB statement. Many procedures do not allow the ATTRIB for a varible to be specified on a temporary basis.

When this data set is the basis of a SAS DATA step view, the TRANSCODE attribute must be reflected in the view.

Run the sample code to see the effect of the problem.

    If you cannot install the HOTFIX, here are two work-arounds for this problem:
  1. Do not use a DATA step view.
  2. Convert the SAS data set to an external file, use FTP in binary mode to transfer the data set to the new platform, read the external data set, rebuild the SAS data set and indexes (if any) on the new platform.


Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemBase SASz/OS9.1 TS1M3 SP49.2 TS2M2
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.1 TS1M3 SP49.2 TS2M2
Microsoft Windows XP 64-bit Edition9.1 TS1M3 SP49.2 TS2M2
Microsoft Windows 2000 Advanced Server9.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server9.1 TS1M3 SP4
Microsoft Windows 2000 Server9.1 TS1M3 SP4
Microsoft Windows 2000 Professional9.1 TS1M3 SP4
Microsoft Windows NT Workstation9.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M3 SP49.2 TS2M2
Microsoft Windows Server 2003 Standard Edition9.1 TS1M3 SP49.2 TS2M2
Microsoft Windows XP Professional9.1 TS1M3 SP49.2 TS2M2
Windows Vista9.1 TS1M3 SP49.2 TS2M2
64-bit Enabled AIX9.1 TS1M3 SP49.2 TS2M2
64-bit Enabled HP-UX9.1 TS1M3 SP49.2 TS2M2
64-bit Enabled Solaris9.1 TS1M3 SP49.2 TS2M2
HP-UX IPF9.1 TS1M3 SP49.2 TS2M2
Linux9.1 TS1M3 SP49.2 TS2M2
Linux on Itanium9.1 TS1M3 SP49.2 TS2M2
OpenVMS Alpha9.1 TS1M3 SP49.2 TS2M2
Solaris for x649.1 TS1M3 SP49.2 TS2M2
Tru64 UNIX9.1 TS1M3 SP49.2 TS2M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.